Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0664

reference: 725-tree-1
name: 0664
tree-preservation-order: undefined
725-tpo-1
uprn
address-text
point: POINT (-0.982272 50.866764)
geometry: MULTIPOLYGON (((-0.982187 50.866754,-0.982191 50.866771,-0.982203 50.866786,-0.982221 50.866798,-0.982245 50.866806,-0.982271 50.866809,-0.982297 50.866807,-0.982321 50.866799,-0.982341 50.866788,-0.982353 50.866773,-0.982357 50.866756,-0.982354 50.866739,-0.982342 50.866724,-0.982323 50.866712,-0.982300 50.866704,-0.982273 50.866701,-0.982247 50.866704,-0.982223 50.866711,-0.982204 50.866723,-0.982192 50.866738,-0.982187 50.866754)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL